What problem is being solved here? Is something not working right now?

it initial crsftokeninterface and csrfmiddleware (which initial csrftokeninterface again and other classes not necessary), it's only need to get a post parameter name and Metatag name, the same names used in csrfmiddleware,

when the page loading it will fetch csrf token twice from session
sorry, forget to update the CsrfviewInjection file

when the page loading it will fetch csrf token twice from session sorry, forget to update the CsrfviewInjection file

Only need to refactor CsrfViewInjection::getCsrfParameters() metod to fix it. Why need another changes?

when the page loading it will fetch csrf token twice from session sorry, forget to update the CsrfviewInjection file

Only need to refactor CsrfViewInjection::getCsrfParameters() metod to fix it. Why need another changes?

here public function getCsrfParameters(): array
{

    $csrf = new Csrf(
        $this->token->getValue(),
        $this->middleware->getParameterName(),
        $this->middleware->getHeaderName(), 
    );

only get $this->middleware->getParameterName(), and
$this->middleware->getHeaderName(), from csrfmiddleware,

it's not necessary to call csrfmiddleware (call csrftokeninterface again and other useless classes,it's not right to call middleware from view),
so add a Csrftrait to define parmater name and header name,
csrfmiddleware and this CsrfViewInjection all get them from Csrftrait,

CsrfViewInjection implements CommonParametersInjectionInterface, MetaTagsInjectionInterface
this will call twice,
so adding only one CsrfParametersInjectionInterface to avoid ,

from the viewrender get CsrfParameters once to an array,
then merge to common parameters and metatag parameters,

Anyway you should get parameter/header name from middleware, becuase it can be not default.

Anyway you should get parameter/header name from middleware, becuase it can be not default.

yes, if it can be config or customized, it needs a new class which read from configuration, then call the class from middleware or view injection,
if call middleware from view, it called csrftokeninterface again and called other classes not necessary,
it may cause other problems for the middleware is called in sequence,